Skip to main content

Send to Production

Overview​

Once the bot does not have any pending bugs, the user entitled as a RPA tester stakeholder who performed the tests can deploy the process to the production environment going through an approval process.

The approval process called Upload package to PRO, is invoked from the Processes in test collection located in My Stuff section. Click Send to production.

LCM_DevCycle_24

The process diagram is the following.

LCM_3uploa

What you need to do?​

When the user entitled as a RPA tester stakeholder clicks Send to production, the task Test result opens. In this task, the tester attaches the document of bot deployment and reviews whether there are not pending bugs.

LCM_DevCycle_25

Note: The process enables a task to cancel the process if required.

Click Next when you have finished. If there are pending bugs to resolve, the procedure cannot continue.

LCM_DevCycle_26

When the process continues, the task Approve is assigned to the tester's boss.

LCM_DevCycle_27

The boss decides whether the bot is approved to be deployed to production environment or not. If the boss rejects the deployment, the procedure finishes.

LCM_DevCycle_28

When the boss approves the deployment, the tester needs to upload the bot package to the Production environment. To upload the package, follow the same instructions explained in Upload a package in Bizagi from step 1.3. Take into account that the available Orchestrators, tenants and user names correspond to the production environment only.